Monolith to Microservices: Sustaining Productivity While Detangling the System
- Downloads：9133
- Type：Epub+TxT+PDF+Mobi
- Create Date：2021-05-22 11:55:02
- Update Date：2025-09-06
- Status：finish
- Author：Sam Newman
- ISBN：1492047848
- Environment：PC/Android/iPhone/iPad/Kindle
- Download
Summary
How do you detangle a monolithic system and migrate it to a microservices architecture？ How do you do it while maintaining business-as-usual？ As a companion to Sam Newman's extremely popular Building Microservices， this new book details a proven method for transitioning an existing monolithic system to a microservice architecture。
With many illustrative examples， insightful migration patterns， and a bevy of practical advice to transition your monolith enterprise into a microservice operation， this practical guide covers multiple scenarios and strategies for a successful migration， from initial planning all the way through application and database decomposition。 You'll learn several tried and tested patterns and techniques that you can use as you migrate your existing architecture。
Ideal for organizations looking to transition to microservices， rather than rebuild
Helps companies determine whether to migrate， when to migrate， and where to begin
Addresses communication， integration， and the migration of legacy systems
Discusses multiple migration patterns and where they apply
Provides database migration examples， along with synchronization strategies
Explores application decomposition， including several architectural refactoring patterns
Delves into details of database decomposition， including the impact of breaking referential and transactional integrity， new failure modes， and more
With many illustrative examples， insightful migration patterns， and a bevy of practical advice to transition your monolith enterprise into a microservice operation， this practical guide covers multiple scenarios and strategies for a successful migration， from initial planning all the way through application and database decomposition。 You'll learn several tried and tested patterns and techniques that you can use as you migrate your existing architecture。
Ideal for organizations looking to transition to microservices， rather than rebuild
Helps companies determine whether to migrate， when to migrate， and where to begin
Addresses communication， integration， and the migration of legacy systems
Discusses multiple migration patterns and where they apply
Provides database migration examples， along with synchronization strategies
Explores application decomposition， including several architectural refactoring patterns
Delves into details of database decomposition， including the impact of breaking referential and transactional integrity， new failure modes， and more
Reviews
Diego Pacheco
，
A good book in coverage but could be better in-depth especially around migrations。
Sindhu
，
This book can introduce you to micro service patterns， case studies and potential issues ！ This can definitely be used as reference when you have a huge monolith（db or service） and you don’t know where to start your decomposition！ P。S。: Chapter 5 is just a brief summary on all the downsides he has been discussing in each section！ Skip it if you have already understood the core idea！ I would give 3。5/5！
Koosh Doc
，
This book seems to be a step 1 if an organization is flirting with the idea of moving from a monolith to microservices。 I like the fact the author is honest about evaluating your needs before allowing yourself to be swept by the herd。 Since I am a part of an organization which has already made the decision to switch to using microservices （and rightly so！！）， it's interesting to know that some issues are quite widespread regardless of which organization you work for and actually see them in front This book seems to be a step 1 if an organization is flirting with the idea of moving from a monolith to microservices。 I like the fact the author is honest about evaluating your needs before allowing yourself to be swept by the herd。 Since I am a part of an organization which has already made the decision to switch to using microservices （and rightly so！！）， it's interesting to know that some issues are quite widespread regardless of which organization you work for and actually see them in front of myself。 The author has identified those issues and has given solutions which are actually being implemented by my team （eg: Strangler Fig， Shims）。 But at some point， one might realize that the author has written things that are quite obvious and seemed repetitive （parity with legacy functionality， end-to-end integration testing， breaking changes）。 It kind of became a drag in the 5th chapter。 。。。more
Jordan Zagham
，
Delivers on the promise to explain challenges and approaches for decomposition。 Concise and to-the-point。 Will be checking out Sam's other book to see if some of the details glossed over in this are covered in more depth。 Delivers on the promise to explain challenges and approaches for decomposition。 Concise and to-the-point。 Will be checking out Sam's other book to see if some of the details glossed over in this are covered in more depth。 。。。more
Ebouks
，
Good introductory to transforming a monolith into a microservices-based system。 It lays out the main ideas nicely。 However， it’s a bit naive and doesn’t touch on real-world systems which are way more complex。Buy the ebook now:Monolith to Microservices: Evolutionary Patterns to Transform Your Monolith 1st Edition Good introductory to transforming a monolith into a microservices-based system。 It lays out the main ideas nicely。 However， it’s a bit naive and doesn’t touch on real-world systems which are way more complex。Buy the ebook now:Monolith to Microservices: Evolutionary Patterns to Transform Your Monolith 1st Edition 。。。more
Regis Hattori
，
This book has some good advice on how to manage an application or database migration in small steps。 The first and last chapters are just an introduction to microservices and their problems。 Nothing new especially for those who have already read "Building Microservices"。The second chapter helps us to plan the migration including the soft skills required。 But more interesting than that， it shows us that depend on the problems we are trying to solve there are some easier and cheaper alternatives t This book has some good advice on how to manage an application or database migration in small steps。 The first and last chapters are just an introduction to microservices and their problems。 Nothing new especially for those who have already read "Building Microservices"。The second chapter helps us to plan the migration including the soft skills required。 But more interesting than that， it shows us that depend on the problems we are trying to solve there are some easier and cheaper alternatives to microservices that do necessarily involve code。 For example， changing the organizational structure or the infrastructure。The third and forth chapters talk about the patterns。 This should be the most important part of the book but I didn't like how the patterns were organized。 Comparing to other "patterns" books like "Design Patterns" and "Enterprise Integration Patterns"， this book is much more disorganized。 One of the most valuable thing about the patterns is that when you read about one of them， you can also have a good overview about other related ones。 Here， the patterns are sometimes compared only in one way。 For example， if patterns A and B are related and B is presented last， the chapter that talks about B will compare it to A but not necessary the other way around。 That way， you can only see the relationship among them if you read them in order。Besides that， some patterns seems not to be very useful。 The most important ones are listed and explained in this talk was made just before this book release:https://www。youtube。com/watch？v=9I9Gd。。。I think it is something between 3 and 4 stars。 I will rate as 4 because it is not easy to find material about it。 。。。more
Lazar Dilov
，
Honestly in the past years I have read a lot of titles about microservices architecture but this one turned out to be actually useful for me and my job。 For the last two years I was desperately trying to get rid of monolithic structured applications and this book gave me the best approaches to do that！ It is fairly simple but really practical and useful！ Congrats to Newman！ Although there were many thing I already knew， there were also some observations and simple advices that can definitely cha Honestly in the past years I have read a lot of titles about microservices architecture but this one turned out to be actually useful for me and my job。 For the last two years I was desperately trying to get rid of monolithic structured applications and this book gave me the best approaches to do that！ It is fairly simple but really practical and useful！ Congrats to Newman！ Although there were many thing I already knew， there were also some observations and simple advices that can definitely change your workflow whenever you are facing such issues。 。。。more
Bartłomiej Falkowski
，
It's so hard to write a good book about software architecture。 I think you have two options: digging deeply into the technical details or trying to be technologicaly agnostic and relying only on "abstractions"。 This book is of the latter type - word "Docker" is used only once and word "Kubernetess" is used less than five times :） And this is a really good book。What I liked:- Simplicity。 All the patterns short and well explained。 Moreover， we always have a context of usage - it's easier to put it It's so hard to write a good book about software architecture。 I think you have two options: digging deeply into the technical details or trying to be technologicaly agnostic and relying only on "abstractions"。 This book is of the latter type - word "Docker" is used only once and word "Kubernetess" is used less than five times :） And this is a really good book。What I liked:- Simplicity。 All the patterns short and well explained。 Moreover， we always have a context of usage - it's easier to put it in the "real-life" scenario。- Pragmatism。 I like the idea of slider instead of button for description of making changes。 Nothing is for free and we should always look at architecture migration in this way。What I didn't like:- The shallowness of some topics。 For example， the phrase "extract your services based on bounded contexts" is in self a topic for multiple books。 However， I understand that exploring such problems in this book would increase the number of pages dramatically :） I accept it。 。。。more
Daniela
，
Um apanhado de boas práticas e exemplos adquiridos pelo autor。 A parte técnica é bem superficial， mas apresenta boas referências
Anjar Priandoyo
，
Actually a good book， but I could not finish it。 I found the best way is to start with basic sofware engineering first
Aaron
，
Great content， very helpful。 The meat of the book could have been organized a bit better， and some topics could have used a bit more expansion。 Could have used more depth on data migration strategies -- the dual write strategy almost completely ignores possible consistency issues due to partial failures。
Kristjan
，
Did not really seek this one for read cover to cover， but pinpoint and learn for my own knowhow （notice didnotfinish shelf reference）。
Jack
，
Newman compiled a decent survey of the different patterns you can use to break apart a monolith。 Unfortunately with this type of book most of the patterns don't apply to your particular situation。 Having said that， the patterns were well explained and for visual learners it includes clear diagrams to illustrate designs。 I'll report back once we break apart our monolith :） Newman compiled a decent survey of the different patterns you can use to break apart a monolith。 Unfortunately with this type of book most of the patterns don't apply to your particular situation。 Having said that， the patterns were well explained and for visual learners it includes clear diagrams to illustrate designs。 I'll report back once we break apart our monolith :） 。。。more
James Pierce
，
While I remain a proponent of microservice architecture。 This book contains within some of the most compelling detractions from the paradigm。
Denis Capeto
，
Excelent。 It was nice to see that we face the same problems when working with microservices and quite frequent end up with the same solutions
Denis Romanovsky
，
A nice book with lots of recepies， patterns and best practices for breaking monoliths into microservices。 Not too detailed into tech stuff， but still good anough。
Ruturaj Vartak
，
I liked the simple thought process that was applied to the this topic， nothing drastic， very objective and cognizant of real-world problems。 Its a must read for all devs， specially guys orchestrating things between multiple teams。
Hosein
，
A very fundamental book which introduces the problems and approaches of the migration to Microservices。 I was already familiar with some topics but enjoyed reading it because there were some edge cases also explained there。
Damian Zydek
，
Why Sam Newman wrote this book？ （IMO）Because as Martin Fowler wrote， "You must be THIS tall to use microservices"。When should I move to microservice architecture？What are the pros and cons of microservice architecture？Which module of my system should I move as first？What is the process of refactoring to microservices？What are the best practices for refactoring to microservices？ What new problems will occur after moving to microservice architecture？This book will help you grow to "THIS" tall by a Why Sam Newman wrote this book？ （IMO）Because as Martin Fowler wrote， "You must be THIS tall to use microservices"。When should I move to microservice architecture？What are the pros and cons of microservice architecture？Which module of my system should I move as first？What is the process of refactoring to microservices？What are the best practices for refactoring to microservices？ What new problems will occur after moving to microservice architecture？This book will help you grow to "THIS" tall by answering those and other questions。 。。。more
Viktor Malyshev
，
Not really a super technical book。 It's about thinking about microservices， resolving problems with it。 And thinking about how to solve those problems。 Key ideas from the book: give yourself time to get better at building microservices and get enough information before actually deciding to go into MS world。 I recommend reading this book to all who are struggling with a monolithic approach where microservices can do the job。 Not really a super technical book。 It's about thinking about microservices， resolving problems with it。 And thinking about how to solve those problems。 Key ideas from the book: give yourself time to get better at building microservices and get enough information before actually deciding to go into MS world。 I recommend reading this book to all who are struggling with a monolithic approach where microservices can do the job。 。。。more
Saran Sivashanmugam
，
Another great microservices book from Sam Newman。 I felt this is a sequel to his earlier book， Building Microservices。 Sam updated some concepts from recent microservices evolution such as choreographed vs orchestrated Sagas， added infrastructure evolution such as Kubernetes。 I loved the depth he covered the monolith database refactoring and the simple but elegant solutions he proposed using schemas and views in existing database engine for refactoring。 I'm a fan of Sam's pragmatic approach when Another great microservices book from Sam Newman。 I felt this is a sequel to his earlier book， Building Microservices。 Sam updated some concepts from recent microservices evolution such as choreographed vs orchestrated Sagas， added infrastructure evolution such as Kubernetes。 I loved the depth he covered the monolith database refactoring and the simple but elegant solutions he proposed using schemas and views in existing database engine for refactoring。 I'm a fan of Sam's pragmatic approach when introducing new concepts that works very well for startups and big corporations。 He also delved in to details about the organizational aspects of microservices and the distributed systems concerns that microservices might bring。 If you liked reading his earlier book Building Microservices， then this is a highly recommended sequel helping in implementing that。 。。。more
Xanan
，
The book approaches the problem of migrating an existing monolithic architecture to a microservice architecture。The book considers technical as well as non-technical issues involved in the migration。The technical part of the book （Chapters 3 and 4） is still very high level。 No programming language is used and no code examples are given。Potential problems and possible solutions are clearly illustrated with pros and cons。The first chapter introduces the monolithic design， its defining characterist The book approaches the problem of migrating an existing monolithic architecture to a microservice architecture。The book considers technical as well as non-technical issues involved in the migration。The technical part of the book （Chapters 3 and 4） is still very high level。 No programming language is used and no code examples are given。Potential problems and possible solutions are clearly illustrated with pros and cons。The first chapter introduces the monolithic design， its defining characteristics， its inherent limitations and how microservices can improve that。Chapter 2 highlights the importance of careful planning before embarking on a migration process。 It suggests the need to consider implications in terms of team organization， skills， and costs。The author also points out that migration to microservices is not a must and in some situations a monolithic design might actually be a better solution。Chapter 3 discusses several patterns that can be used to incrementally migrate selected functionalities into a microservice。It explores possible alternative solutions to common problems and describes positive and negative aspects of each。Chapter 4 focuses on how a database that backs a monolith affects and is affected by the migration of some functionality to a microservice。Splits and non splits solutions are considered together with repercussions on data access and transactions。Chapter 5 is a sort of troubleshooting summary where potential migration problems are reviewed with solutions。 "Building Microservices" is another other book from the author that partly overlaps with this one but discusses microservices from a more general point of view。"Monolith to Microservices" focuses more on the problem of migrating an existing monolithic system to one based on microservices。In the book you will read several times "if you want to know more about this read my other book Building Microservices"。I found this very annoying。 。。。more
Fermin Quant
，
A very well written book， which shows in every page the experience of the author on the topic。 It really puts into perspective the huge task of moving to microservices from a monolith， the most common pitfalls， and provides possible solutions to them。 The book is mostly useful as a reference for your journey of moving to microservices， it is not an absolute proven guide of not failing， but more a collection of very well organized experiences that will help you avoid most common problems and kind A very well written book， which shows in every page the experience of the author on the topic。 It really puts into perspective the huge task of moving to microservices from a monolith， the most common pitfalls， and provides possible solutions to them。 The book is mostly useful as a reference for your journey of moving to microservices， it is not an absolute proven guide of not failing， but more a collection of very well organized experiences that will help you avoid most common problems and kind of guide your decision making。 It is good that the author emphasizes at the start that microservices is not for every situation， and spends some time explaining how you can figure this out for your current situation before you start。 。。。more
Isaac Perez Moncho
，
Very good book， if you are thinking about microservices you must read it。It explains the different ways you can migrate from a monolith to microservices， but also tries to explain how to understand if this move is right for you。A brief summary would be: "strangler patter" and it's not easy。 Very good book， if you are thinking about microservices you must read it。It explains the different ways you can migrate from a monolith to microservices， but also tries to explain how to understand if this move is right for you。A brief summary would be: "strangler patter" and it's not easy。 。。。more
adnan rafiq
，
Pure excellence - must read It is an amazing book。 It covers everything from start to end。 If you want to travel the road of Microservices。 It’s structured in a way that fits the mental model of monolith developers but to evaluate Microservices architecture。 It’s going to serve a glossary of what to do & what not to do when doing Microservices。 Starts with simple 3 questions， during the journey you would feel yeah it feels very real。 But without single line of code。 You will get answers along th Pure excellence - must read It is an amazing book。 It covers everything from start to end。 If you want to travel the road of Microservices。 It’s structured in a way that fits the mental model of monolith developers but to evaluate Microservices architecture。 It’s going to serve a glossary of what to do & what not to do when doing Microservices。 Starts with simple 3 questions， during the journey you would feel yeah it feels very real。 But without single line of code。 You will get answers along the way， from people problems， team ownership， tackling database， importance of DDD and suggestions on tool one has to learn along the way。 Thanks Sam Newman for writing such an amazing book。 。。。more
Alexander Holbreich
，
Good overview to migration patterns。 But do not expect deep discussion on any of pattern or tools。#microservices
Ibrahim Tasyurt
，
I loved this book。 The author puts together the challenges&opportunities when a transforming monolith to micro-services。 Also compiles the patterns to migrate the code and data。 The patterns described in this book is not only applicable to micros-ervices transformation but any kind of re-write and migration cases。
Ali Bicak
，
Practical concise guide for migrating monolithic systems to microservices with discussion on decomposition issues。
Victor
，
Practical advice on how to move to Microservices。 It also discusses the reasons you would want to migrate your app to a Microservices architectural style and even gives alternatives that might help you achieve the same goal without migrating。 I liked the realistic examples， trade-off analysis。I enjoyed Chapter 4， on Decomposing the Database the most， because I think that's probably the hardest part when migrating to Microservices （and the one that gets the least amount of coverage in many resour Practical advice on how to move to Microservices。 It also discusses the reasons you would want to migrate your app to a Microservices architectural style and even gives alternatives that might help you achieve the same goal without migrating。 I liked the realistic examples， trade-off analysis。I enjoyed Chapter 4， on Decomposing the Database the most， because I think that's probably the hardest part when migrating to Microservices （and the one that gets the least amount of coverage in many resources）。 The patterns cover problems we've all seen in the wild and the solutions are pragmatic and useful。 。。。more
Jakub
，